<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
<head>
<title>Open Object Rexx - Interpreter Source Files</title> <meta
http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
</head>
<body>

   <h1>Open Object Rexx - Files</h1>

   <h1>Interpreter Source Files</h1>

   <p>This is the main subdirectory for the core interpreter source files.
      These files are used the build the rexx shared library.  The interpreter
      is organized into a a number of different subsystems, each with a unique
      subdirectory.</p>

   <p>The following are the available subdirectories.</p>


   <table border="0">
      <tr>
         <td valign="top"><a href="./api/files.html">api</a></td>
         <td valign="top">Files related to APIs involving calls into the interpreter
            functions.</td>
      </tr>
      <tr>
         <td valign="top"><a href="./behaviour/files.html">behaviour</a></td>
         <td valign="top">Source files related to the underlying ooRexx object model.  The
            files in this directory are used to create the object method
            diectionary and associated type codes.</td>
      </tr>
      <tr>
         <td valign="top"><a href="./classes/files.html">classes</a></td>
         <td valign="top">All externally visible ooRexx classes.  These are the core
            classes visible to ooRexx programs.</td>
      </tr>
      <tr>
         <td valign="top"><a
            href="./concurrency/files.html">concurrency</a></td>
         <td valign="top">Interpreter synchronization and threading support.</td>
      </tr>
      <tr>
         <td valign="top"><a href="./execution/files.html">execution</a></td>
         <td valign="top">Classes used to manage the execution state of running ooRexx
            code.  This includes call contexts, variable management, etc.</td>
      </tr>
      <tr>
         <td valign="top"><a href="expression/files.html">expression</a></td>
         <td valign="top">Runtime support for different categories of expression terms
            (operators, method calls, functions, variables, etc.)</td>
      </tr>
      <tr>
         <td valign="top"><a
            href="./instructions/files.html">instructions</a></td>
         <td valign="top">The implementations of the ooRexx keyword instructions and
            directives.</td>
      </tr>
      <tr>
         <td valign="top"><a href="./memory/files.html">memory</a></td>
         <td valign="top">The ooRexx garbage collector and memory manager.  The memory
            management functions include the initial image bootstrap
            processing.</td>
      </tr>
      <tr>
         <td valign="top"><a href="./messages/files.html">messages</a></td>
         <td valign="top">Platform-independent error message files.  The error message
            files are generated from a single source XML file using XSLT
            transforms.</td>
      </tr>
      <tr>
         <td valign="top"><a href="./package/files.html">package</a></td>
         <td valign="top">Source files for package/external library management
            subsystem.</td>
      </tr>
      <tr>
         <td valign="top"><a href="./parser/files.html">parser</a></td>
         <td valign="top">Files used to translate ooRexx source into an executable format.
            </td>
      </tr>
      <tr>
         <td valign="top"><a href="./platform/files.html">platform</a></td>
         <td valign="top">The portion of the interpreter core that is implemented by
            platform-specific code.  The interface between the portable core is
            defined in terms of classes that must be implemented by each
            platform execution layer.  Each supported platform environment is
            contained in a subdirectory of platform.
            </td>
      </tr>
      <tr>
         <td valign="top"><a href="./RexxClasses/files.html">RexxClasses</a></td>
         <td valign="top">The portion of the interpreter core that is
            implemented on ooRexx code.  These files are loaded during the
            rexximage build step, and are saved in ready-to-use form inside the
            generated rexx.img file.
            </td>
      </tr>
      <tr>
         <td valign="top"><a href="./runtime/files.html">runtime</a></td>
         <td valign="top">Core interpreter runtime support.  This is the portion
            of code that defines the core interpreter and manages active
            interpreter instances.  This is also where many of the core
            interpreter data areas and constant definitions are located.
            </td>
      </tr>
      <tr>
         <td valign="top"><a
            href="./streamlibrary/files.html">streamlibrary</a></td>
         <td valign="top">The native methods that implement the .Stream class.
            These are implemented as external library methods so that
            interpreter I/O does not block multi-threaded execution while
            reading/writing.
            </td>
      </tr>
   </table>


</body>
</html>

